Appropriate level of abstraction for groupware in the LLM era
Appropriate level of abstraction for groupware in the LLM era
Summary: In the age of LLM, the current level of abstraction in groupware may not be appropriate and may need to be closer to customer operations.gpt.icon
[What I thought while listening to the last session of Matsuo Lab Summer School 2023 Large-Scale Language Models.
Groupware is an abstraction of each company's "business" and provides services for the common parts.
Its design was abstracted based on the perception of the world before the advent of LLM
I don't see how the appropriate abstraction layer in the with LLM era is where it is now...
But the current abstraction may not be correct regarding how to leverage that correspondence to create customer value.
Maybe I need to get closer to customer operations.
Considering the addition of LLM functionality as a generic feature based on the current product design implicitly assumes the current level of abstraction
---
This page is auto-translated from /nishio/LLM時代のグループウェアの適切な抽象レベル using DeepL. If you looks something interesting but the auto-translated English is not good enough to understand it, feel free to let me know at @nishio_en. I'm very happy to spread my thought to non-Japanese readers.